tsconfck

What is tsconfck?

The tsconfck package is a utility for TypeScript configuration management. It helps in resolving and loading TypeScript configuration files (tsconfig.json) by handling inheritance and references within these configurations. This is particularly useful in complex projects where tsconfig settings are split across multiple files or extended from other configurations.

What are tsconfck's main functionalities?

Load and resolve tsconfig.json

This feature allows loading a tsconfig.json file, resolving all its extends and references to provide a final resolved configuration object. It handles the asynchronous nature of file reading and parsing, providing a promise-based API.

const { loadTsconfig } = require('tsconfck');

loadTsconfig('path/to/tsconfig.json').then(tsconfig => {
  console.log(tsconfig);
}).catch(error => {
  console.error(error);
});

Other packages similar to tsconfck

tsconfig-paths

tsconfig-paths is a package that helps in resolving and loading paths from tsconfig.json files for module resolution. Unlike tsconfck, which focuses more broadly on configuration loading and resolution, tsconfig-paths specifically targets path resolution to aid in module loading in non-TypeScript environments.

tsconfig-loader

tsconfig-loader provides functionality to load tsconfig.json files without resolving the entire configuration. It's simpler than tsconfck as it does not handle the resolution of 'extends' or other complex configurations, focusing instead on direct loading of configurations as they are defined.

README

tsconfck

A utility to find and parse tsconfig files without depending on typescript

Why

Because no simple official api exists and tsconfig.json isn't actual json.

Features

• find closest tsconfig.json
• convert tsconfig.json to actual json and parse it
• resolve "extends"
• resolve "references" of solution-style tsconfig
• optional findNative and parseNative to use official typescript api
• zero dependencies (typescript optional)
• extensive testsuite

Install

npm install --save-dev tsconfck # or pnpm, yarn

Usage

without typescript installed

import { parse } from 'tsconfck';
const {
	tsconfigFile, // full path to found tsconfig
	tsconfig, // tsconfig object including merged values from extended configs
	extended, // separate unmerged results of all tsconfig files that contributed to tsconfig
	solution, // solution result if tsconfig is part of a solution
	referenced // referenced tsconfig results if tsconfig is a solution
} = await parse('foo/bar.ts');

with typescript

import { parseNative } from 'tsconfck';
const {
	tsconfigFile, // full path to found tsconfig
	tsconfig, // tsconfig object including merged values from extended configs, normalized
	result, // output of ts.parseJsonConfigFileContent
	solution, // solution result if tsconfig is part of a solution
	referenced // referenced tsconfig results if tsconfig is a solution
} = await parseNative('foo/bar.ts');

API

see API-DOCS

Advanced

caching

You can use a map to cache results and avoid reparsing if you process multiple ts files that share few tsconfig files

import { parse } from 'tsconfck';
// 1. create cache instance
const cache = new Map();
// 2. pass cache instance in options
const fooResult = await parse('src/foo.ts', { cache });
// 3. profit (if they share the same tsconfig.json, it is not parsed again)
const barResult = await parse('src/bar.ts', { cache });

You are responsible for clearing the cache if tsconfig files change on disk during its lifetime.

Always clear the whole cache if anything changes as objects in the cache can ref each other

Returned results are direct cache objects.

If you want to modify them, deep-clone first.

reduce fs.stat overhead

You can specify a root directory and provide a set of known tsconfig locations to improve performance in large projects

import { parse, findAll } from 'tsconfck';
const root = '.';
const tsConfigPaths = new Set([
	...(await findAll(root, { skip: (dir) => dir === 'node_modules' || dir === '.git' }))
]);
const cache = new Map();
const parseOptions = { cache, root, tsConfigPaths };
// these calls use minimal fs
const fooResult = await parse('src/foo.ts', parseOptions);
const barResult = await parse('src/bar.ts', parseOptions);

Using the root option can lead to errors if there is no tsconfig inside root.

You are responsible for updating tsConfigPaths if tsconfig files are added/removed on disk during its lifetime.

error handling

find and parse reject for all errors they encounter.

For parse, you can choose to resolve with an empty result instead if no tsconfig file was found

import { parse } from 'tsconfck';
const result = await parse('some/path/without/tsconfig/foo.ts', {
	resolveWithEmptyIfConfigNotFound: true
});
// result = { tsconfigFile: 'no_tsconfig_file_found',tsconfig: {} }

TSConfig type (optional, requires typescript as devDependency)

import type { TSConfig } from 'pkg-types';

Check out https://github.com/unjs/pkg-types

cli

A simple cli wrapper is included, you can use it like this

find

# prints /path/to/tsconfig.json on stdout
tsconfck find src/index.ts

find-all

# prints all tsconfig.json in dir on stdout
tsconfck find-all src/

parse

# print content of ParseResult.tsconfig on stdout
tsconfck parse src/index.ts

# print to file
tsconfck parse src/index.ts > output.json

parse-result

# print content of ParseResult on stdout
tsconfck parse-result src/index.ts

# print to file
tsconfck parse-result src/index.ts > output.json

help

# print usage
tsconfck -h # or --help, -?, help

Links

• changelog

Develop

This repo uses

• pnpm
• conventional-changelog/commitlint

In addition to default commit-msg prefixes you can use 'wip: ' for commit messages in branches. PRs are going to be squash-merged

# install dependencies
pnpm install
# run tests
pnpm test
#run tests in watch mode (doesn't require dev in parallel)
pnpm test:watch

License

MIT